Make ResponseUtil internal#49153
Conversation
|
@javache has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
|
@mateoguzmana not sure if this is actually a valid use case: Anyway I think we should mark this as breaking in the changelog |
|
This pull request was successfully merged by @mateoguzmana in 360cbf7 When will my fix make it into a release? | How to file a pick request? |
@cortinico hmm, good point, that's an interesting one. I didn't see much usage/recent activity on the repository so didn't consider it very relevant – but still maybe I could create an issue on their side to let them be aware of this breaking change. Wdyt? Curious to see how some similar cases have been handled so I can follow up as well on that |
I think in this particular case we can create an issue on their end, saying that this function is going away. Either use an alternative or fork the code. I was exploring using shepherd for similar scenarios in the future: https://github.com/NerdWalletOSS/shepherd |
Summary:
As part of the initiative to reduce the public API surface, this class can be internalized. I've checked there are no relevant OSS usages.
Changelog:
[INTERNAL] - Make com.facebook.react.modules.network.ResponseUtil internal
Test Plan: